home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / p_man / cat2 / standard / plock.z / plock
Encoding:
Text File  |  1998-10-20  |  5.6 KB  |  133 lines
  1.  
  2.  
  3.  
  4. pppplllloooocccckkkk((((2222))))                                                              pppplllloooocccckkkk((((2222))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _pppp_llll_oooo_cccc_kkkk - lock into memory or unlock process, text, or data
  10.  
  11. CCCC SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_ssss_yyyy_ssss_////_llll_oooo_cccc_kkkk_...._hhhh_>>>>
  13.  
  14.      _iiii_nnnn_tttt _pppp_llll_oooo_cccc_kkkk_((((_iiii_nnnn_tttt _oooo_pppp_))))_;;;;
  15.  
  16. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  17.      _pppp_llll_oooo_cccc_kkkk allows the calling process to lock into memory or unlock its text
  18.      segment (text lock), its data segment (data lock), or both its text and
  19.      data segments (process lock).  Locked segments are immune to all routine
  20.      swapping.  The calling process must have the super-user privilege to use
  21.      this call.
  22.  
  23.      _pppp_llll_oooo_cccc_kkkk does not lock down memory which has been mapped into the address
  24.      space of a process via the _mmmm_mmmm_aaaa_pppp(2) system call (e.g., IRIX Arenas).
  25.      These mmaped memory regions may be locked down using one of the following
  26.      system calls: _mmmm_pppp_iiii_nnnn(2), _mmmm_llll_oooo_cccc_kkkk(3C), _mmmm_llll_oooo_cccc_kkkk_aaaa_llll_llll(3C).
  27.  
  28.      _pppp_llll_oooo_cccc_kkkk does not lock down the stack of the calling process.  The stack of
  29.      a process can only be locked into memory with the _mmmm_llll_oooo_cccc_kkkk_aaaa_llll_llll(3C) system
  30.      call.
  31.  
  32.      _pppp_llll_oooo_cccc_kkkk performs the function specified by _o_p:
  33.  
  34.           _PPPP_RRRR_OOOO_CCCC_LLLL_OOOO_CCCC_KKKK    Lock text and data segments into memory (process lock).
  35.  
  36.           _TTTT_XXXX_TTTT_LLLL_OOOO_CCCC_KKKK     Lock text segment into memory (text lock).
  37.  
  38.           _DDDD_AAAA_TTTT_LLLL_OOOO_CCCC_KKKK     Lock data segment into memory (data lock).
  39.  
  40.           _UUUU_NNNN_LLLL_OOOO_CCCC_KKKK      Remove locks.
  41.  
  42.      _pppp_llll_oooo_cccc_kkkk fails and does not perform the requested operation if one or more
  43.      of the following are true:
  44.  
  45.      _EEEE_PPPP_EEEE_RRRR_MMMM          The calling process does not have the super-user
  46.                     privilege.
  47.  
  48.      _EEEE_IIII_NNNN_VVVV_AAAA_LLLL         _o_p is equal to _PPPP_RRRR_OOOO_CCCC_LLLL_OOOO_CCCC_KKKK and a process lock, a text lock,
  49.                     or a data lock already exists on the calling process.
  50.  
  51.      _EEEE_IIII_NNNN_VVVV_AAAA_LLLL         _o_p is equal to _TTTT_XXXX_TTTT_LLLL_OOOO_CCCC_KKKK and a text lock, or a process lock
  52.                     already exists on the calling process.
  53.  
  54.      _EEEE_IIII_NNNN_VVVV_AAAA_LLLL         _o_p is equal to _DDDD_AAAA_TTTT_LLLL_OOOO_CCCC_KKKK and a data lock, or a process lock
  55.                     already exists on the calling process.
  56.  
  57.      _EEEE_IIII_NNNN_VVVV_AAAA_LLLL         _o_p is equal to _UUUU_NNNN_LLLL_OOOO_CCCC_KKKK and no lock exists on the calling
  58.                     process.
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. pppplllloooocccckkkk((((2222))))                                                              pppplllloooocccckkkk((((2222))))
  71.  
  72.  
  73.  
  74.      _EEEE_AAAA_GGGG_AAAA_IIII_NNNN         Not enough memory.
  75.  
  76. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  77.      _iiii_nnnn_tttt_rrrr_oooo(2), _eeee_xxxx_eeee_cccc(2), _eeee_xxxx_iiii_tttt(2), _ffff_oooo_rrrr_kkkk(2), _gggg_eeee_tttt_rrrr_llll_iiii_mmmm_iiii_tttt(2), _mmmm_llll_oooo_cccc_kkkk(3C),
  78.      _mmmm_llll_oooo_cccc_kkkk_aaaa_llll_llll(3C), _mmmm_pppp_iiii_nnnn(2), _mmmm_eeee_mmmm_cccc_nnnn_tttt_llll(2), _ssss_hhhh_mmmm_cccc_tttt_llll(2), _uuuu_llll_iiii_mmmm_iiii_tttt(2).
  79.  
  80. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  81.      Upon successful completion, a value of 0 is returned to the calling
  82.      process.  Otherwise, a value of -1 is returned and _eeee_rrrr_rrrr_nnnn_oooo is set to
  83.      indicate the error.
  84.  
  85. WWWWAAAARRRRNNNNIIIINNNNGGGG
  86.      The _pppp_llll_oooo_cccc_kkkk function and _mmmm_llll_oooo_cccc_kkkk_aaaa_llll_llll_////_mmmm_uuuu_nnnn_llll_oooo_cccc_kkkk_aaaa_llll_llll pair provide similar
  87.      functionality. Developers should choose the set that best suites their
  88.      application and stick with it, as mixing the interfaces may result in
  89.      unexpected behavior.
  90.  
  91.  
  92.  
  93.  
  94.  
  95.  
  96.  
  97.  
  98.  
  99.  
  100.  
  101.  
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.